| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.5.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.5.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_5_1_Clinical_Task_Creation__Assignment_and_Routing |
| Title | AS.5.1 Clinical Task Creation, Assignment and Routing (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Creation, assignment, delegation, and/or transmission of tasks to the appropriate parties. |
| Purpose | A "Task" is a specific piece of work or duty that is assigned to a person or entity. A task often needs to be accomplished within a defined period of time or by a deadline. Tasks are often managed by an activity (or project) tracking mechanism (e.g., as part of an automated business rule process). Tasks are determined by the specific needs of patients and practitioners in a care setting. Task creation may be automated, where appropriate. An example of a system-triggered task is when laboratory results are received electronically; a task to review the result is automatically generated and assigned to a responsible party. Tasks are at all times assigned to at least one user or role for disposition. Whether the task is assignable and to whom the task can be assigned will be determined by the specific needs of practitioners in a care setting. Task-assignment lists help users prioritize and complete assigned tasks. For example, after receiving communication (e.g., a phone call or e-mail) from a patient, the triage nurse routes or assigns a task to return the patient's call to the physician who is on call physician. Another example is for a urinalysis, the nurse routes or assigns a task to clinical staff to collect a urine specimen, and for the results to be routed to the responsible physician and person ordering the test. Task creation and assignment may be automated, where appropriate. An example is when (International Normalized Ratio) INR results are received they should be automatically routed and assigned to the staff person in the clinic responsible for managing all of the patients that are having INR tests done. Task assignment ensures that all tasks are disposed of by the appropriate person or role and allows efficient interaction of entities in the care process. When a task is assigned to more than one individual or role, an indication is required to show whether the task must be completed by all individuals/roles or if only one completion suffice. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Creation, assignment, delegation, and/or transmission of tasks to the appropriate parties.
A "Task" is a specific piece of work or duty that is assigned to a person or entity. A task often needs to be accomplished within a defined period of time or by a deadline. Tasks are often managed by an activity (or project) tracking mechanism (e.g., as part of an automated business rule process). Tasks are determined by the specific needs of patients and practitioners in a care setting. Task creation may be automated, where appropriate. An example of a system-triggered task is when laboratory results are received electronically; a task to review the result is automatically generated and assigned to a responsible party. Tasks are at all times assigned to at least one user or role for disposition. Whether the task is assignable and to whom the task can be assigned will be determined by the specific needs of practitioners in a care setting.
Task-assignment lists help users prioritize and complete assigned tasks. For example, after receiving communication (e.g., a phone call or e-mail) from a patient, the triage nurse routes or assigns a task to return the patient's call to the physician who is on call physician. Another example is for a urinalysis, the nurse routes or assigns a task to clinical staff to collect a urine specimen, and for the results to be routed to the responsible physician and person ordering the test. Task creation and assignment may be automated, where appropriate. An example is when (International Normalized Ratio) INR results are received they should be automatically routed and assigned to the staff person in the clinic responsible for managing all of the patients that are having INR tests done. Task assignment ensures that all tasks are disposed of by the appropriate person or role and allows efficient interaction of entities in the care process. When a task is assigned to more than one individual or role, an indication is required to show whether the task must be completed by all individuals/roles or if only one completion suffice.
| AS.5.1#01 | SHALL |
The system SHALL provide the ability to capture new tasks. |
| AS.5.1#02 | SHOULD |
The system SHOULD provide the ability to auto-populate task information based on rules, patient information, triggering events, and/or resource factors. |
| AS.5.1#03 | SHALL |
The system SHALL provide the ability for the user to enter and update an assignment for a task to one or more individuals or roles. |
| AS.5.1#04 | SHOULD |
The system SHOULD provide the ability to capture oral (e.g., telephone, voice-over-IP or in-person) communication between providers and patients or their representatives (including the identification of the providers). |
| AS.5.1#05 | SHALL |
The system SHALL provide the ability to determine and update an assignment for a task to one or more individuals or clinical roles, based on workflow rules. |
| AS.5.1#06 | SHOULD |
The system SHOULD provide the ability to determine workflow task routing to individuals or roles in succession or in parallel. |
| AS.5.1#07 | SHOULD |
The system SHOULD provide the ability to determine workflow task routing to multiple individuals or roles in succession or in parallel based on status and workflow rules. |
| AS.5.1#08 | SHOULD |
The system SHOULD provide the ability to capture and update priorities for tasks. |
| AS.5.1#09 | SHOULD |
The system SHOULD provide the ability to determine and update priorities for tasks (e.g., based on urgency assigned to the task, clinical rules and business rules). |
| AS.5.1#10 | dependent SHOULD |
The system SHOULD provide the ability to capture restrictions for task assignment based on an appropriate role according to organizational policy. |
| AS.5.1#11 | dependent SHOULD |
The system SHOULD determine restrictions for task assignment based on appropriate role according to organizational policy. |
| AS.5.1#12 | SHALL |
The system SHALL provide the ability to update the priorities of clinical tasks (e.g., to ensure timely completion). |
| AS.5.1#13 | dependent SHOULD |
The system SHOULD determine and update the priorities of clinical tasks according to organizational policy (e.g., to ensure timely completion). |
| AS.5.1#14 | SHOULD |
The system SHOULD provide the ability to transmit task assignment with request for confirmation to external systems that participate in completion of the task (e.g., task requesting patient transportation OR request for meeting between providers). |
| AS.5.1#15 | SHOULD |
The system SHOULD provide the ability to render a list of tasks by user or user role according to user specified criteria. |
| AS.5.1#16 | SHOULD |
The system SHOULD provide the ability to determine time periods and recipients for notification of overdue medication administrations. |
| AS.5.1#17 | SHOULD |
The system SHOULD provide the ability to render a notification to the clinician of overdue medication administrations. |
| AS.5.1#18 | SHOULD |
The system SHOULD provide the ability to determine time periods for order expiration for types of orders. |
| AS.5.1#19 | SHOULD |
The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders due to expire. |
| AS.5.1#20 | SHOULD |
The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders requiring signature (e.g., verbal and telephone orders, co-signature). |
| AS.5.1#21 | dependent SHOULD |
The system SHOULD provide the ability to enter and maintain the clinical task assignments and pre-conditions expected for performance of identified/selected health care procedures according to scope of practice, organizational policy, and/or jurisdictional law. |
| AS.5.1#22 | SHOULD |
The system SHOULD provide the ability to capture, maintain, and render information regarding the reassignment of a single task or group of tasks to available roles when the primary role that was selected is not available. |
| AS.5.1#23 | dependent conditional SHOULD |
IF the system determines that applicable tasks and pre-conditions expected have not been performed, THEN the system SHOULD transmit a notification to a patient's provider or to the patient's care team according to scope of practice, organizational policy, and/or jurisdictional law. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.5.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Creation, assignment, delegation, and/or transmission of tasks to the appropriate parties.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>A "Task" is a specific piece of work or duty that is assigned to a person or entity. A task often needs to be accomplished within a defined period of time or by a deadline. Tasks are often managed by an activity (or project) tracking mechanism (e.g., as part of an automated business rule process). Tasks are determined by the specific needs of patients and practitioners in a care setting. Task creation may be automated, where appropriate. An example of a system-triggered task is when laboratory results are received electronically; a task to review the result is automatically generated and assigned to a responsible party. Tasks are at all times assigned to at least one user or role for disposition. Whether the task is assignable and to whom the task can be assigned will be determined by the specific needs of practitioners in a care setting.</p>\n<p>Task-assignment lists help users prioritize and complete assigned tasks. For example, after receiving communication (e.g., a phone call or e-mail) from a patient, the triage nurse routes or assigns a task to return the patient's call to the physician who is on call physician. Another example is for a urinalysis, the nurse routes or assigns a task to clinical staff to collect a urine specimen, and for the results to be routed to the responsible physician and person ordering the test. Task creation and assignment may be automated, where appropriate. An example is when (International Normalized Ratio) INR results are received they should be automatically routed and assigned to the staff person in the clinic responsible for managing all of the patients that are having INR tests done. Task assignment ensures that all tasks are disposed of by the appropriate person or role and allows efficient interaction of entities in the care process. When a task is assigned to more than one individual or role, an indication is required to show whether the task must be completed by all individuals/roles or if only one completion suffice.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to capture new tasks.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to auto-populate task information based on rules, patient information, triggering events, and/or resource factors.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability for the user to enter and update an assignment for a task to one or more individuals or roles.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture oral (e.g., telephone, voice-over-IP or in-person) communication between providers and patients or their representatives (including the identification of the providers).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to determine and update an assignment for a task to one or more individuals or clinical roles, based on workflow rules.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine workflow task routing to individuals or roles in succession or in parallel.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine workflow task routing to multiple individuals or roles in succession or in parallel based on status and workflow rules.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and update priorities for tasks.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine and update priorities for tasks (e.g., based on urgency assigned to the task, clinical rules and business rules).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture restrictions for task assignment based on an appropriate role according to organizational policy.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine restrictions for task assignment based on appropriate role according to organizational policy.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to update the priorities of clinical tasks (e.g., to ensure timely completion).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#13</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine and update the priorities of clinical tasks according to organizational policy (e.g., to ensure timely completion).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#14</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to transmit task assignment with request for confirmation to external systems that participate in completion of the task (e.g., task requesting patient transportation OR request for meeting between providers).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#15</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a list of tasks by user or user role according to user specified criteria.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#16</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine time periods and recipients for notification of overdue medication administrations.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#17</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification to the clinician of overdue medication administrations.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#18</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to determine time periods for order expiration for types of orders.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#19</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders due to expire.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#20</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders requiring signature (e.g., verbal and telephone orders, co-signature).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#21</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to enter and maintain the clinical task assignments and pre-conditions expected for performance of identified/selected health care procedures according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#22</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain, and render information regarding the reassignment of a single task or group of tasks to available roles when the primary role that was selected is not available.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.5.1#23</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n <i>conditional</i>\n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>IF the system determines that applicable tasks and pre-conditions expected have not been performed, THEN the system SHOULD transmit a notification to a patient's provider or to the patient's care team according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.5.1",
"version" : "2.1.0",
"name" : "AS_5_1_Clinical_Task_Creation__Assignment_and_Routing",
"title" : "AS.5.1 Clinical Task Creation, Assignment and Routing (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Creation, assignment, delegation, and/or transmission of tasks to the appropriate parties.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "A \"Task\" is a specific piece of work or duty that is assigned to a person or entity. A task often needs to be accomplished within a defined period of time or by a deadline. Tasks are often managed by an activity (or project) tracking mechanism (e.g., as part of an automated business rule process). Tasks are determined by the specific needs of patients and practitioners in a care setting. Task creation may be automated, where appropriate. An example of a system-triggered task is when laboratory results are received electronically; a task to review the result is automatically generated and assigned to a responsible party. Tasks are at all times assigned to at least one user or role for disposition. Whether the task is assignable and to whom the task can be assigned will be determined by the specific needs of practitioners in a care setting. \n\nTask-assignment lists help users prioritize and complete assigned tasks. For example, after receiving communication (e.g., a phone call or e-mail) from a patient, the triage nurse routes or assigns a task to return the patient's call to the physician who is on call physician. Another example is for a urinalysis, the nurse routes or assigns a task to clinical staff to collect a urine specimen, and for the results to be routed to the responsible physician and person ordering the test. Task creation and assignment may be automated, where appropriate. An example is when (International Normalized Ratio) INR results are received they should be automatically routed and assigned to the staff person in the clinic responsible for managing all of the patients that are having INR tests done. Task assignment ensures that all tasks are disposed of by the appropriate person or role and allows efficient interaction of entities in the care process. When a task is assigned to more than one individual or role, an indication is required to show whether the task must be completed by all individuals/roles or if only one completion suffice.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-01",
"label" : "AS.5.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to capture new tasks.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-02",
"label" : "AS.5.1#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to auto-populate task information based on rules, patient information, triggering events, and/or resource factors.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-03",
"label" : "AS.5.1#03",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability for the user to enter and update an assignment for a task to one or more individuals or roles.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-04",
"label" : "AS.5.1#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture oral (e.g., telephone, voice-over-IP or in-person) communication between providers and patients or their representatives (including the identification of the providers)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-05",
"label" : "AS.5.1#05",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to determine and update an assignment for a task to one or more individuals or clinical roles, based on workflow rules."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-06",
"label" : "AS.5.1#06",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine workflow task routing to individuals or roles in succession or in parallel.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-07",
"label" : "AS.5.1#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine workflow task routing to multiple individuals or roles in succession or in parallel based on status and workflow rules."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-08",
"label" : "AS.5.1#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and update priorities for tasks.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#7"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-09",
"label" : "AS.5.1#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine and update priorities for tasks (e.g., based on urgency assigned to the task, clinical rules and business rules)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.1-10",
"label" : "AS.5.1#10",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture restrictions for task assignment based on an appropriate role according to organizational policy.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#8"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.1-11",
"label" : "AS.5.1#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine restrictions for task assignment based on appropriate role according to organizational policy."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-12",
"label" : "AS.5.1#12",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to update the priorities of clinical tasks (e.g., to ensure timely completion).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.3.1.1#9"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.1-13",
"label" : "AS.5.1#13",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine and update the priorities of clinical tasks according to organizational policy (e.g., to ensure timely completion)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-14",
"label" : "AS.5.1#14",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to transmit task assignment with request for confirmation to external systems that participate in completion of the task (e.g., task requesting patient transportation OR request for meeting between providers)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-15",
"label" : "AS.5.1#15",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a list of tasks by user or user role according to user specified criteria."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-16",
"label" : "AS.5.1#16",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine time periods and recipients for notification of overdue medication administrations."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-17",
"label" : "AS.5.1#17",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification to the clinician of overdue medication administrations."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-18",
"label" : "AS.5.1#18",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to determine time periods for order expiration for types of orders."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-19",
"label" : "AS.5.1#19",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders due to expire."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-20",
"label" : "AS.5.1#20",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a notification to the ordering clinician concerning orders requiring signature (e.g., verbal and telephone orders, co-signature)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.1-21",
"label" : "AS.5.1#21",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to enter and maintain the clinical task assignments and pre-conditions expected for performance of identified/selected health care procedures according to scope of practice, organizational policy, and/or jurisdictional law."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.5.1-22",
"label" : "AS.5.1#22",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain, and render information regarding the reassignment of a single task or group of tasks to available roles when the primary role that was selected is not available."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-AS.5.1-23",
"label" : "AS.5.1#23",
"conformance" : [
"SHOULD"
],
"conditionality" : true,
"requirement" : "IF the system determines that applicable tasks and pre-conditions expected have not been performed, THEN the system SHOULD transmit a notification to a patient's provider or to the patient's care team according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.